Details

Problem

Tailwind v4 (specifically via its dependency jiti) and modern Node.js ecosystems have moved towards using the node: prefix for built-in module imports (e.g., require("node:module")).

The current Parcel version used in Plasmo (2.9.3) does not support the node: prefix for CommonJS dependencies, leading to the following build error:
Could not resolve module "node:module"

This issue has been a major blocker for users trying to adopt Tailwind v4 (#1188).

Solution

This PR upgrades the internal Parcel dependency stack from 2.9.3 to 2.13.2+.

Key changes:

• Upgraded all @parcel/* packages to versions matching parcel@2.13.2.
• Correctly mapped package-specific version diversions to satisfy peer dependencies (e.g., @parcel/graph@3.3.2, @parcel/hash@2.9.3).
• Upgraded @parcel/watcher to 2.5.6.

Verification:

• Ran pnpm install across the workspace to ensure lockfile consistency.
• Successfully built the CLI and core packages using pnpm build:cli.
• Confirmed that Parcel 2.10.0+ explicitly supports node: prefix resolution (ref: parcel-bundler/parcel#9244).

This is a structural fix at the bundler level rather than a temporary workaround like patching node_modules.

Related Issues

• Fixes [BUG] Error: Could not resolve module "node:module" in jiti after upgrading to Tailwind v4 in Plasmo #1188

Code of Conduct

• I agree to follow this project's Code of Conduct
• I agree to license this contribution under the MIT LICENSE
• I checked the current PR for duplication.